-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Source Zendesk Support: Replace ZendeskSupportAuditLogsIncrementalSync with low-code #53620
Source Zendesk Support: Replace ZendeskSupportAuditLogsIncrementalSync with low-code #53620
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
/format-fix
|
ah sorry my mistake, I didn't realize we'd already kicked off a run. thanks @DanyloGL . If we see no mismatches on |
@brianjlai, regression looks not bad. Affected stream retrieves the same amount of records. On tested connection |
@DanyloGL excellent! Can you start a progressive rollout by modifying the image tags and merge this PR in? and nice work @pabloescoder |
…ortAuditLogsIncrementalSync
/format-fix
|
…ortAuditLogsIncrementalSync
…ortAuditLogsIncrementalSync
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Starting Progressive Rollout
What
Resolves https://github.com/airbytehq/airbyte-internal-issues/issues/11511
How
By replacing ZendeskSupportAuditLogsIncrementalSync with low-code DatetimeBasedCursor and adding a request param to filter records by stream_interval start and end time.
Review guide
manifest.yaml
components.py
User Impact
No impact, enables concurrent CDK framework.
Can this PR be safely reverted and rolled back?
Acceptance Criteria